Skip to content

CLOUDP-341681 - create patchqa alias for non static only #369

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 3 commits into from
Aug 28, 2025
Merged

CLOUDP-341681 - create patchqa alias for non static only #369

merged 3 commits into from
Aug 28, 2025

Conversation

nammn
Copy link
Collaborator

@nammn nammn commented Aug 26, 2025 •
edited
Loading

Summary

This pull request updates the tagging strategy for build variants in .evergreen.yml to better distinguish between "static" and "non-static" (now labeled as cloudqa_non_static) test suites. The changes mainly introduce new tags to build variants and update the relevant patch alias, which will help with more granular test selection and filtering in CI pipelines.

Key changes:

Tagging improvements for build variants:

  • Added the cloudqa_non_static tag to all non-static CloudQA-related build variants, and updated the patch-run-cloudqa alias to target this new tag instead of the previous cloudqa tag. -> when releasing cloudqa we don't need to "test" static variants

  • Added the static tag to all static build variants, including static CloudQA, static smoke, static multi-cluster, and static OM test variants.

These changes allow for more precise control over which test suites are run in different contexts, improving maintainability and CI efficiency.

Proof of Work

  • ci is starting and .evergreen.yml works
  • manual run: Link

Checklist

  • Have you linked a jira ticket and/or is the ticket in the title?
  • Have you checked whether your jira ticket required DOCSP changes?
  • Have you added changelog file?

@nammn nammn requested a review from a team as a code owner August 26, 2025 09:44
@github-actions GitHub Actions
Copy link

⚠️ (this preview might not be accurate if the PR is not rebased on current master branch)

MCK 1.3.0 Release Notes

New Features

Multi-Architecture Support

We've added comprehensive multi-architecture support for the kubernetes operator. This enhancement enables deployment on IBM Power (ppc64le) and IBM Z (s390x) architectures alongside
existing x86_64 support. Core images (operator, agent, init containers, database, readiness probe) now support multiple architectures. We do not add support IBM and ARM support for Ops-Manager and the init-ops-manager image.

Bug Fixes

  • This change fixes the current complex and difficult-to-maintain architecture for stateful set containers, which relies on an "agent matrix" to map operator and agent versions which led to a sheer amount of images.
  • We solve this by shifting to a 3-container setup. This new design eliminates the need for the operator-version/agent-version matrix by adding one additional container containing all required binaries. This architecture maps to what we already do with the mongodb-database container.
  • Fixed an issue where the readiness probe reported the node as ready even when its authentication mechanism was not in sync with the other nodes, potentially causing premature restarts.

Other Changes

  • Optional permissions for PersistentVolumeClaim moved to a separate role. When managing the operator with Helm it is possible to disable permissions for PersistentVolumeClaim resources by setting operator.enablePVCResize value to false (true by default). When enabled, previously these permissions were part of the primary operator role. With this change, permissions have a separate role.
  • subresourceEnabled Helm value was removed. This setting used to be true by default and made it possible to exclude subresource permissions from the operator role by specifying false as the value. We are removing this configuration option, making the operator roles always have subresource permissions. This setting was introduced as a temporary solution for this OpenShift issue. The issue has since been resolved and the setting is no longer needed.
  • We have deliberately not published the container images for OpsManager versions 7.0.16, 8.0.8, 8.0.9 and 8.0.10 due to a bug in the OpsManager which prevents MCK customers to upgrade their OpsManager deployments to those versions.

@nammn nammn added the skip-changelog Use this label in Pull Request to not require new changelog entry file label Aug 26, 2025
@anandsyncs
Copy link
Contributor

LGTM, I am curious to know the cost savings per year from this.

@nammn nammn changed the title create patchqa alias for non static only CLOUDP-341681 - create patchqa alias for non static only Aug 28, 2025
@nammn nammn merged commit 9102033 into master Aug 28, 2025
35 of 37 checks passed
@nammn nammn deleted the fix-patch-run-ccloudqa branch August 28, 2025 14:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@m1kola m1kola m1kola approved these changes

@anandsyncs anandsyncs anandsyncs approved these changes

@viveksinghggits viveksinghggits Awaiting requested review from viveksinghggits viveksinghggits is a code owner automatically assigned from mongodb/kubernetes-hosted

@lsierant lsierant Awaiting requested review from lsierant

@mircea-cosbuc mircea-cosbuc Awaiting requested review from mircea-cosbuc

Assignees
No one assigned
Labels
skip-changelog Use this label in Pull Request to not require new changelog entry file
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@nammn @anandsyncs @m1kola